This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Yes, by signficantly reducing the rows, it will help in performance.
Also, just a reminder, if you have the same @dblookup, and performance is critical, I would consider using the "cache" funtionality or "" for the default to cache in your @dblookup. This is most appropriate if data does not change much.
Then, when users add or remove records / documents that may affect those views, you can put an agent to simply do a view.refresh on the server after those documents are saved.
Another reference I came across in the past is to try writing some lookups in LotusScript to see if that helps. Using view.getdocumentbykey or building a notesnavigator can be incredibly effective in some situations.
-Kyle Huang
Feedback response number WEBB8MBPNW created by ~John Reniskiikle on 10/04/2011
also, remember the "cache"
Return to top
. . . . . . also, remember the "cache" (~John Reniskiik... 4.Oct.11) 
